ntg-context wrote:
> On 2021-11-24, Aditya Mahajan via ntg-context wrote:
> > I don't know what is the current state of context syntax highlighting
> > support in vim/neovim (I use a highly modifies syntax file). It will
> > be nice to have support of \startMP(code|p
On 2021-11-24, Aditya Mahajan via ntg-context wrote:
> I don't know what is the current state of context syntax highlighting
> support in vim/neovim (I use a highly modifies syntax file). It will
> be nice to have support of \startMP(code|page) and \startluacode to do
> syntax
..) which could be integrated.
I don't know what is the current state of context syntax highlighting support
in vim/neovim (I use a highly modifies syntax file). It will be nice to have
support of \startMP(code|page) and \startluacode to do syntax highlighting for
metapost and lua. Metafun has
> Am 01.09.2021 um 14:45 schrieb Hans Hagen via ntg-context
> :
>
> On 9/1/2021 2:19 PM, Henning Hraban Ramm via ntg-context wrote:
>> Hi, I’m trying to “translate” the documentation of “fiziko”* from LaTeX to
>> ConTeXt and would like to avoid the doubling of M
On 9/1/2021 2:19 PM, Henning Hraban Ramm via ntg-context wrote:
Hi, I’m trying to “translate” the documentation of “fiziko”* from LaTeX to
ConTeXt and would like to avoid the doubling of MP code like:
\startMP
path p;
p := (0,0){dir(30)}..(5cm, 0)..{dir(30)}(10cm, 0);
draw brush
Hi, I’m trying to “translate” the documentation of “fiziko”* from LaTeX to
ConTeXt and would like to avoid the doubling of MP code like:
\startMP
path p;
p := (0,0){dir(30)}..(5cm, 0)..{dir(30)}(10cm, 0);
draw brush (p)(2minStrokeWidth*sin(offsetPathLength*pi));
\stopMP
\startMPcode
h,frame=on,offset=1cc,]
# >\setuptyping[MP][before={\startMPT},after={\stopMPT},]
# >\startMP bla \stopMP
# >\stoptext
# >
# >Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as
TL2019)
# >and I have got _two_ boxes -- the outer one is correct and frames the typing
wframe\defineframedtext[MPT][background="" class="">\setuptyping[MP][before={\startMPT},after={\stopMPT},]\startMP bla \stopMP\stoptextNow I tried it with ConTeXt from TL2019 (TL2018 produces the same result as TL2019)and I have got _two_ boxes -- the outer one is correct and fr
,frame=on,offset=1cc,]
\setuptyping[MP][before={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext
Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as
TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing
environment
as in the past
={\startMPT},after={\stopMPT},]
\startMP bla \stopMP
\stoptext
Now I tried it with ConTeXt from TL2019 (TL2018 produces the same result as
TL2019)
and I have got _two_ boxes -- the outer one is correct and frames the typing
environment
as in the past whereas the new box frames the text inside
:
\startMP
draw (0,0) withpen pencircle 1in withcolor red ;
\stopMP
\stoptext
%——
I obtain a color syntax output (« draw » in red, « within » in green for
example). This code does not work anymore in MKIV (every word is the
same color, green). There should be a solution ?
Hard to say without
Dear list,
I’m using colored verbatim code (for course notes). In the past, I modified
verb-mp.mkii for the langage I need (SAS). This code works fine with MKII:
%——
\setupcolors[state=start]
\definetyping [MP] [option=MP]
\starttext
A example:
\startMP
draw (0,0) withpen pencircle 1in
by ctrl-o) and it works inside \startMP...\stopMP... blocks.
Doesn't that work for you?
Maybe you expected the suggestions to pop-up without pressing any key?
For that, you
need a plugin like NeoComplete or AutoComplPop.
Nicola
$ and a$ text objects;
>
> - better integration with MetaPost (indentation and autocompletion
> inside \startMP...\stopMP... works automatically);
>
> - syntax highglighting can be enabled for any nested filetype (MetaPost
> and Lua are enabled by default);
>
> - compiler
a paragraph);
- i$ and a$ text objects;
- better integration with MetaPost (indentation and autocompletion
inside \startMP...\stopMP... works automatically);
- syntax highglighting can be enabled for any nested filetype (MetaPost
and Lua are enabled by default);
- compiler plugin, supporting
, 46291 },
[startLuaSnippetNameCore]={ 127, 245803, 61132 },
[startLuaSnippetNameLibraries]={ 127, 246257, 38877 },
[startLuaSnippetQuote]={ 127, 246898, 19907 },
[startLuaSnippetSpecial]={ 127, 247006, 23901 },
[startLuaSnippetString]={ 127, 246646, 61126 },
[startMP]={ 127, 245820, 14236
Matthijs Kooijman wrote:
Hi all,
according to the wiki, and the current code, the arguments to
\installprettytype should be uppercased. E.g.:
because want uppercase
\startTEX
\stopTEX
\startMP
\stopMP
\startLUA
\stopLUA
\installprettytype [PHP][PHP]
Referring to them should
17 matches
Mail list logo
